-
-
Notifications
You must be signed in to change notification settings - Fork 718
chore(deps): update all non-major dependencies #3526
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for GitHub.
|
commit: |
Deploying content with
|
Latest commit: |
ce84159
|
Status: | ✅ Deploy successful! |
Preview URL: | https://a08fa60b.content-f0q.pages.dev |
Branch Preview URL: | https://renovate-all-minor-patch.content-f0q.pages.dev |
82d5eba
to
c7d2980
Compare
c7d2980
to
3606879
Compare
3606879
to
b886e8f
Compare
️✅ There are no secrets present in this pull request anymore.If these secrets were true positive and are still valid, we highly recommend you to revoke them. 🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request. |
b886e8f
to
4288ced
Compare
4288ced
to
f88d235
Compare
f88d235
to
72a797b
Compare
72a797b
to
ec30d2d
Compare
ec30d2d
to
2a3582a
Compare
2a3582a
to
2f0f857
Compare
2f0f857
to
e73d88f
Compare
30948f8
to
c229ed9
Compare
c229ed9
to
a918207
Compare
a918207
to
197f235
Compare
197f235
to
57f8f5b
Compare
57f8f5b
to
45351ea
Compare
45351ea
to
0055f6b
Compare
0055f6b
to
0a2a6d9
Compare
0a2a6d9
to
2882a30
Compare
2882a30
to
a3bd353
Compare
a3bd353
to
d74d320
Compare
d74d320
to
7d20ac5
Compare
7d20ac5
to
932b76d
Compare
932b76d
to
0e68146
Compare
0e68146
to
ce84159
Compare
Note
Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to
mend[bot]
.This notice will be removed on 2025-10-07.
This PR contains the following updates:
^4.20250910.0
->^4.20251004.0
^2.6.3
->^2.6.5
^4.0.0
->^4.0.1
^3.12.2
->^3.13.0
^1.2.21
->^1.2.23
^24.3.1
->^24.6.2
^1.0.0
->^1.3.0
^12.2.0
->^12.4.1
^3.2.0
->^3.3.0
^0.3.2
->^0.3.4
^9.35.0
->^9.37.0
^2.5.1
->^2.6.1
^0.6.1
->^0.6.2
10.15.1
->10.18.0
^19.0.4
->^19.0.5
^3.12.2
->^3.13.0
^7.4.3
->^7.5.1
5.9.2
->5.9.3
^1.0.0
->^1.1.0
^3.0.6
->^3.1.0
^4.35.0
->^4.42.0
Release Notes
cloudflare/workerd (@cloudflare/workers-types)
v4.20251004.0
Compare Source
v4.20251003.0
Compare Source
v4.20251001.0
Compare Source
nuxt/ui (@nuxt/ui)
v4.0.1
Compare Source
Bug Fixes
img
role (066b8a1), closes #5044parts
(ff67fa3)data-orientation
for consistency (a9fe7c6)default-open
(22ee075), closes #5112ckb
translations (#5079) (3ee3a5e)⎋
toEsc
(#5076) (64d1589)useCookie
stub with nuxt's default value handling (#5089) (f531807)fabian-hiller/valibot (@valibot/to-json-schema)
v1.1.0
Compare Source
Many thanks to @EltonLobo07, @sacrosanctic, @muningis, @EskiMojo14, @MOZGIII, @vktrl and @jasperteo for contributing to this release.
message
method to overwrite local error message configuration of a schema (pull request #1103)summarize
method to summarize issues into a pretty-printable multi-line string (pull request #1158)getTitle
,getDescription
andgetMetadata
methods to extract metadata of a schema (pull request #1154)minEntries
andmaxEntries
validation action to validate number of object entries (pull request #1100)entries
andnotEntries
validation action to validate number of object entries (pull request #1156)parseJson
andstringifyJson
transformation action to parse and stringify JSON (pull request #1137)flavor
transformation action to flavor the output type of a schema (pull request #950)multipleOf
validation action (pull request #1164)variant
andvariantAsync
schema to improve performance by aborting validation of discriminators early (pull request #1110)NanoIDAction
andNanoIDIssue
interface toNanoIdAction
andNanoIdIssue
(pull request #1171)MarkOptional
type to fix input and output type of objects in edge cases (issue #1176)WiseLibs/better-sqlite3 (better-sqlite3)
v12.4.1
Compare Source
What's Changed
Full Changelog: WiseLibs/better-sqlite3@v12.4.0...v12.4.1
v12.3.0
Compare Source
What's Changed
windows-2022
by @m4heshd in #1388New Contributors
Full Changelog: WiseLibs/better-sqlite3@v12.2.0...v12.3.0
unjs/db0 (db0)
v0.3.4
Compare Source
compare changes
📦 Build
❤️ Contributors
v0.3.3
Compare Source
compare changes
🚀 Enhancements
dispose
andusing createDatabase()
(#178)💅 Refactors
📖 Documentation
🏡 Chore
❤️ Contributors
eslint/eslint (eslint)
v9.37.0
Compare Source
unjs/jiti (jiti)
v2.6.1
Compare Source
compare changes
🩹 Fixes
📦 Build
terser-webpack-plugin
(#407)🏡 Chore
❤️ Contributors
pnpm/pnpm (pnpm)
v10.18.0
Compare Source
Minor Changes
Added network performance monitoring to pnpm by implementing warnings for slow network requests, including both metadata fetches and tarball downloads.
Added configuration options for warning thresholds:
fetchWarnTimeoutMs
andfetchMinSpeedKiBps
.Warning messages are displayed when requests exceed time thresholds or fall below speed minimums
Related PR: #10025.
Patch Changes
minimumReleaseAge
configuration #10030.cleanupUnusedCatalogs
configuration when removing dependent packages.scriptShell
is set tofalse
#8748.pnpm dlx
should not fail whenminimumReleaseAge
is set #10037.v10.17.1
Compare Source
Patch Changes
minimumReleaseAge
setting, print this information out in the error message #9974.state.json
creation path when executingpnpm patch
in a workspace project #9733.minimumReleaseAge
is set and thelatest
tag is not mature enough, prefer a non-deprecated version as the newlatest
#9987.v10.17.0
Compare Source
Minor Changes
The
minimumReleaseAgeExclude
setting now supports patterns. For instance:Related PR: #9984.
Patch Changes
minimumReleaseAge
check, when the package is requested by exact version and the packument is loaded from cache #9978.minimumReleaseAge
is set and the active version under a dist-tag is not mature enough, do not downgrade to a prerelease version in case the original version wasn't a prerelease one #9979.v10.16.1
Compare Source
Patch Changes
v10.16.0
Compare Source
Minor Changes
There have been several incidents recently where popular packages were successfully attacked. To reduce the risk of installing a compromised version, we are introducing a new setting that delays the installation of newly released dependencies. In most cases, such attacks are discovered quickly and the malicious versions are removed from the registry within an hour.
The new setting is called
minimumReleaseAge
. It specifies the number of minutes that must pass after a version is published before pnpm will install it. For example, settingminimumReleaseAge: 1440
ensures that only packages released at least one day ago can be installed.If you set
minimumReleaseAge
but need to disable this restriction for certain dependencies, you can list them under theminimumReleaseAgeExclude
setting. For instance, with the following configuration pnpm will always install the latest version of webpack, regardless of its release time:Related issue: #9921.
Added support for
finders
#9946.In the past,
pnpm list
andpnpm why
could only search for dependencies by name (and optionally version). For example:prints the chain of dependencies to any installed instance of
minimist
:What if we want to search by other properties of a dependency, not just its name? For instance, find all packages that have
react@17
in their peer dependencies?This is now possible with "finder functions". Finder functions can be declared in
.pnpmfile.cjs
and invoked with the--find-by=<function name>
flag when runningpnpm list
orpnpm why
.Let's say we want to find any dependencies that have React 17 in peer dependencies. We can add this finder to our
.pnpmfile.cjs
:Now we can use this finder function by running:
pnpm will find all dependencies that have this React in peer dependencies and print their exact locations in the dependency graph.
It is also possible to print out some additional information in the output by returning a string from the finder. For example, with the following finder:
Every matched package will also print out the license from its
package.json
:Patch Changes
nodeVersion
is not set to an exact semver version #9934.pnpm publish
should be able to publish a.tar.gz
file #9927.pnpm run
return a non-zero exit code #9626.microsoft/TypeScript (typescript)
v5.9.3
Compare Source
cloudflare/workers-sdk (wrangler)
v4.42.0
Compare Source
Minor Changes
103fbf0
Thanks @petebacondarwin! - Allow WRANGLER_SEND_ERROR_REPORTS env var to override whether to report Wrangler crashes to SentryPatch Changes
#10757
59d5911
Thanks @dario-piotrowicz! - fixconsole.debug
logs not being logged at theinfo
level (as users expect)Updated dependencies [
2594130
]:v4.41.0
Compare Source
Minor Changes
#10507
21a0bef
Thanks @dario-piotrowicz! - Add strict mode for thewrangler deploy
commandAdd a new flag:
--strict
that makes thewrangler deploy
command be more strict and not deploy workers when the deployment could be potentially problematic. This "strict mode" currently only affects non-interactive sessions where conflicts with the remote settings for the worker (for example when the worker has been re-deployed via the dashboard) will cause the deployment to fail instead of automatically overriding the remote settings.#10710
7f2386e
Thanks @penalosa! - Add prompt to resource creation flow allowing for newly created resources to be remote.Patch Changes
#10822
4c06766
Thanks @edmundhung! - fix: skip banner when using--json
flag inwrangler pages deployment
commands#10838
d3aee31
Thanks @edmundhung! - fix: skip banner when using--json
flag inwrangler queues subscription
commands#10829
59e8ef0
Thanks @edmundhung! - fix: skip banner when using--json
flag inwrangler pipelines
commands#10764
79a6b7d
Thanks @emily-shen! - containers: defaultmax_instances
to 20 instead of 1.#10844
7a4d0da
Thanks @mikenomitch! - Adds new Container instance types, and renamedev
tolite
andstandard
tostandard-1
. The new instance_types are now:#10634
62656bd
Thanks @emily-shen! - fix: error if the container image uri has an account id that doesn't match the current account#10761
886e577
Thanks @petebacondarwin! - switch zone route warning to an info message#10734
8d7f32e
Thanks @penalosa! - Improve formatting of logged errors in some cases#10832
f9d37db
Thanks @petebacondarwin! - retry subdomain requests to be more resilient to flakes#10770
835d6f7
Thanks @danielrs! - Enabling or disablingworkers_dev
is often an indication thatthe user is also trying to enable or disable
preview_urls
. Warn theuser when these enter mixed state.
#10764
79a6b7d
Thanks @emily-shen! - fix: respect the log level set by wrangler when logging using @cloudflare/cliUpdated dependencies [
c8d5282
,bffd2a9
]:v4.40.3
Compare Source
Patch Changes
#10602
ff82d80
Thanks @tukiminya! - fix: update Secrets Store command status from alpha to open-beta#10623
7a6381c
Thanks @IRCody! - Handle more cases for correctly resolving the full uri for an image when using containers push.#10779
325d22e
Thanks @hoodmane! - Add fallthrough: true for python_modules data rule#10112
8d07576
Thanks @devin-ai-integration! - fix: allow Workflow bindings when calling getPlatformProxy()Workflow bindings are not supported in practice when using
getPlatformProxy()
.But their existence in a Wrangler config file should not prevent other bindings from working.
Previously, calling
getPlatformProxy()
would crash if there were any Workflow bindings defined.Now, instead, you get a warning telling you that these bindings are not available.
#10769
0a554f9
Thanks @penalosa! - Mark more errors asUserError
to disable Sentry reporting#10679
6244a9e
Thanks @KianNH! - Fix rendering for nested objects incontainers list
andcontainers info [ID]
#10785
d09cab3
Thanks @pombosilva! - Workflows names and instance IDs are now properly validated with production limits.Updated dependencies [
6ff41a6
,0c208e1
,2432022
,d0801b1
,0a554f9
]:Configuration
📅 Schedule: Branch creation - "on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.